Conversation
Add documentation for continuous backup, point-in-time recovery (PITR), related configuration, commands, and administration updates.
| Running incremental backups on a regular schedule reduces WAL retention on the source cluster for tables under continuous backup, | ||
| because WALs are read from the WAL directory rather than from the source cluster. |
There was a problem hiding this comment.
I'm a bit confused about this part. In the previous section you mentioned
When incremental backups are run for tables that have continuous backup enabled, the backup process
reads WALs from the WAL directory instead of collecting them from the source cluster. This eliminates
the need to retain WALs on the source cluster between incremental backup runs and reduces pressure on
the source cluster's log management.
Which means to me that with Continuous Backup we don't need to keep WAL files in the cluster at all, while the above comment suggests that we need to keep WAL files in the cluster between incrementals. Which one is true?
|
|
||
| The following is an outline of the steps and examples of commands that are used to backup the data for the _green_ application and | ||
| to recover the data later. All commands are run when logged in as HBase superuser. | ||
| The following workflow outlines the steps to back up and recover the _green_ application data. All |
There was a problem hiding this comment.
Instead of overwriting this section with the more advanced Continuous Backup case, I think we might want to keep the original one as well and outline the differences between the two workflows in a separate example for the same green scenario.
3 participants
Update Backup and Restore document to include continuous backup, point-in-time recovery (PITR), related configuration, commands, and administration updates.